monitoring: add consolidated workloads CPU/memory dashboard#209
Closed
ejahnGithub wants to merge 5 commits intosigstore:mainfrom
Closed
monitoring: add consolidated workloads CPU/memory dashboard#209ejahnGithub wants to merge 5 commits intosigstore:mainfrom
ejahnGithub wants to merge 5 commits intosigstore:mainfrom
Conversation
Adds a single GCP Monitoring dashboard that surfaces CPU and memory
across all Sigstore GKE workloads (grouped by namespace / container),
so oncall does not have to navigate multiple metric pages while
investigating resource issues.
The dashboard includes:
- CPU usage in cores (rate of core_usage_time)
- Memory used (non-evictable bytes)
- CPU/memory limit utilization (REDUCE_MAX so a hot replica is visible)
- CPU/memory request utilization (REDUCE_MAX)
- Container restart deltas
- Node CPU allocatable utilization
Resolves sigstore/public-good-instance#1122
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Eugene Jahn <ejahn@sigstore.dev>
The xyChart threshold schema does not accept color/direction for these chart types; the dashboard create rejects them. Keep just the value. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Eugene Jahn <ejahn@sigstore.dev>
Heights of 16 in a 12-column mosaic produced very tall narrow tiles. Use h=4 (standard) for charts and keep h=4 for the overview banner. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Eugene Jahn <ejahn@sigstore.dev>
ejahnGithub
force-pushed
the
workloads-cpu-memory-dashboard
branch
from
e5d92ad to
939aeed
Compare
…iles to workloads dashboard Mirrors the standard GKE Workloads dashboard so oncall does not have to navigate to multiple pages to find resource usage charts: - Pod network received / sent (per namespace) - Ephemeral storage used (per container) - Node memory allocatable utilization (sibling of node CPU) - Running containers per namespace (uptime count) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Eugene Jahn <ejahn@sigstore.dev>
Previous tile used ALIGN_COUNT + REDUCE_SUM, which sums sample counts within the alignment window and is an approximation of container count. Switch to ALIGN_MEAN per series + REDUCE_COUNT across series so the y-axis is the exact number of running containers per namespace. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Eugene Jahn <ejahn@sigstore.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a single GCP Monitoring dashboard
Workloads CPU & Memorythat consolidates CPU and memory across all Sigstore GKE workloads (grouped by namespace / container_name), so oncallers do not have to navigate multiple metric pages while investigating resource issues.It includes (per namespace / container):
Testing
terraform fmt -recursivecleanWill roll out to staging first via the usual Sigstore CI flow once merged.
Issue
Resolves sigstore/public-good-instance#1122